home *** CD-ROM | disk | FTP | other *** search
- Path: camelot.dsccc.com!kcline
- From: kcline@sun132.spd.dsccc.com (Kevin Cline)
- Newsgroups: comp.lang.c++,rec.games.programmer,alt.msdos.programmer,comp.programming
- Subject: Re: Young programmers read me.
- Date: 9 Apr 1996 19:42:36 GMT
- Organization: DSC Communications Corporation Switch Products Division
- Message-ID: <4keejc$lpi@tpd.dsccc.com>
- References: <4icpp9$7hr@barad-dur.nas.com> <aidan-0404961557290001@meathook.intac.com> <3165AD94.6F3A@datalytics.com> <j-jahnke-0604960016160001@ntcs-ip8.uchicago.edu>
- NNTP-Posting-Host: sun132.spd.dsccc.com
-
- In article <j-jahnke-0604960016160001@ntcs-ip8.uchicago.edu>,
- Jerome Jahnke <j-jahnke@uchicago.edu> wrote:
- >I personally
- >can't read some styles on C and C++[;] the guys that put the starting brace
- >on the same line as a conditional or a loop drive me batty and I need to
- >use CDent to change the code just so I can read it.
-
- This should not be a problem if the code is properly indented, ala
-
- if (something_happened) {
- do_something_else();
- }
-
- There is something to be said for conserving screen real-estate.
- I have worked on hard-copy terminals, then on 24x80 screens, then
- on workstations. Workstations are better because I can see more code
- at one time, unless someone wastes all the lines with whitespace and
- braces.
-
- >And if you think about it, it is a lot easier to find a BEGIN and END in a
- >chunk of code than a { and }. They are just bigger and easier to spot.
-
- If the code follows any reasonable indentation style, BEGIN and END add
- no information. They are important to the compiler, but not very important
- to me, trying to read the code, since they don't do anything.
- I don't want them to take up a lot of visual space.
-
- Would prose be easier to read if the punctuation took more room
- INTERROGATION I think not PERIOD
-
-
-
-
- --
- Kevin Cline
-